HDDS-14467. Expose pending delete bytes/namespace in OzoneBucket. #9708
+102
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smengcl
reviewed
Feb 5, 2026
Comment on lines
1302
to
1336
| @@ -1330,6 +1332,8 @@ public List<OzoneBucket> listBuckets(String volumeName, String bucketPrefix, | |||
| .setSourceBucket(bucket.getSourceBucket()) | |||
| .setUsedBytes(bucket.getTotalBucketSpace()) | |||
| .setUsedNamespace(bucket.getTotalBucketNamespace()) | |||
| .setPendingDeleteBytes(bucket.getSnapshotUsedBytes()) | |||
| .setPendingDeleteNamespace(bucket.getSnapshotUsedNamespace()) | |||
Contributor
There was a problem hiding this comment.
Thanks @sadanand48 for the patch.
Let's document the behavior of PendingDeleteBytes / PendingDeleteNamespace (e.g. not accounting for keys that are not recursed yet).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
After HDDS-13756, OzoneBucket.usedBytes is populated from OmBucketInfo.getTotalBucketSpace() (used + snapshotUsed bytes), which makes bucket usage ambiguous after key deletion. This change adds explicit pendingDeleteBytes / pendingDeleteNamespace fields to OzoneBucket to clarify retained bytes (snapshots or pending delete).
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-14467
How was this patch tested?
Unit tests